dependency: Update dependency net.kyori:blossom to v2 #1029
+1
−1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
|
Note Reviews pausedUse the following commands to manage reviews:
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Join our Discord community for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/net.kyori-blossom-2.x
branch
from
61feec1 to
27f9d93
Compare
|
@coderabbitai ignore |
✅ Actions performedReviews paused. |
Renovate Ignore NotificationBecause you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.3.1->2.1.0Release Notes
KyoriPowered/blossom (net.kyori:blossom)
v2.1.0: 🌼 blossom 2.1.0blossom 2.1.0 is a feature release introducing some minor QOL features, and fixing handling of included files. It should be a straightforward upgrade for existing users of Blossom 2.0.1.
✨ Features
varianttemplate property when using variants by @jpenilla in https://github.com/KyoriPowered/blossom/pull/37🐛 Fixes
Full Changelog: KyoriPowered/blossom@v2.0.1...v2.1.0
v2.0.1: 🌼 blossom 2.0.1A hotfix release for blossom 2.0.0. See its release notes for information about the major changes in that release.
🐛 Fixes
Full Changelog: KyoriPowered/blossom@v2.0.0...v2.0.1
v2.0.0: 🌼 blossom 2.0.0NOTE 2.0.1 has been released as a hotfix to this version, resolving an issue with applying headers. See its release notes for details about those changes. We recommend using 2.0.1 instead, but the following release notes still provide helpful migration advice.
Blossom 2.0.0 is a complete redesign of the Blossom plugin to provide a fully featured solution for source and resource templating. It is based on the template engine used to build Sponge's
mathlibrary. See the README for an introduction to Blossom v2's features.Migrating from Blossom v1
The key difference in functionality with v2 is that only source files within the specific templates root will be processed as templates -- all other source files will have no other change.
This allows more efficient execution since templates only need to be regenerated when there are actual changes, and means that any compile errors in non-templated files will be linked correctly in IDE logs. Template output will also be exposed correctly to any IDE run configurations, since templates are processed at project import time.
The quickest migration from v1 starts with a buildscript like:
sourceSets { main { blossom { javaSources { // template values here property("token", value) } } } }Then place files that should be processed as templates in
src/main/java-templates. These are Pebble templates, so the variable syntax is{{ token }}. See their documentation for more of the language's features.Substitute
javawithgroovy,kotlin, orscalaas desired.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.